docs(routing-peers): apply outstanding feedback and expand inbound links#730
Merged
SunsetDrifter merged 3 commits intomainfrom May 5, 2026
Merged
docs(routing-peers): apply outstanding feedback and expand inbound links#730SunsetDrifter merged 3 commits intomainfrom
SunsetDrifter merged 3 commits intomainfrom
Conversation
- Drop the unverified Cloud-specific settings subsection (AWS/GCP/Azure bullets) and the related AWS source/destination pitfall bullet - Spell out "high availability" in the Masquerade note for clarity
…Work Surface the routing peer primer from 11 high-leverage pages so readers landing in a configuration or scenario guide can find the mental model without having to backtrack through the sidebar. - Index pages (manage/networks, manage/network-routes): move the cross-link from the page top into the Routing Peer(s) subsection, where it sits adjacent to existing routing-peer guidance - exit-nodes scenario: cross-link inside the Routing Peer subsection, anchored at #exit-node-mode - internal-dns-servers: cross-link under Domain Resources and Routing Peer DNS, anchored at #routing-peer-dns-resolution - Procedural and comparison pages (access-control, by-scenario VPN-to-Site guides, site-to-site overview, Kubernetes operator, routing peers in Kubernetes): cross-link near the page top with section-specific anchors
emrcbrn
requested changes
May 5, 2026
Contributor
emrcbrn
left a comment
emrcbrn
left a comment
There was a problem hiding this comment.
LGTM - other than one abbreviation usage for HA as well
- Index-page cross-link notes (manage/networks, manage/network-routes): expand "HA" to "high availability" in the bullet list - Primer page: spell out the three remaining HA references in the High availability section and Common pitfalls; use "highly available peers" as the adjective form
emrcbrn
approved these changes
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #727. Two commits:
1. Apply outstanding review feedback
Three small edits to the primer that were applied during review of #727 but never made it into the merged commit:
Cloud-specific settingssubsection and the related AWS source/destination pitfall bullet2. Expand inbound cross-links
Surface the primer from 11 high-leverage pages so readers landing in a configuration or scenario guide can find the mental model without backtracking through the sidebar.
manage/networks,manage/network-routes): move the existing cross-link from the page top into the Routing Peer(s) subsectionexit-nodes: cross-link inside the Routing Peer subsection (anchor#exit-node-mode)internal-dns-servers: cross-link under Domain Resources and Routing Peer DNS (anchor#routing-peer-dns-resolution)access-control,access-home-devices,cloud-to-on-premise,remote-worker-access,site-to-site,routing-peers-and-kubernetes,manage/integrations/kubernetesDraft pending review.